test(adaptive-quality): guard tier cost-monotonicity invariant#148
Merged
Conversation
A richer quality tier must never render less work than a cheaper one (smaller attachment preview, higher label-LOD threshold, or a disabled effect a lower tier enables). The existing suite only guarded maxInitialNodes; this locks the same invariant across attachmentPreviewSize, labelLodZoom, and the four effect flags — the config-regression class that would let a 'lower' tier paradoxically do MORE work. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🧪 Comprehensive Test Suite
Full-stack smoke gate runs in the CI workflow. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a unit guard so a richer quality tier can never render less work than a cheaper one — across
attachmentPreviewSize,labelLodZoom, and the four effect flags. The existing suite only guardedmaxInitialNodes.Motivated by a dashboard FPS anomaly (LOW dragFps < HIGH dragFps in a stale scale-sweep sample): even though the current
BASE_PROFILESare correct, nothing locked the invariant against future config drift.Pure test addition — no production code touched. Full adaptiveQuality suite: 31/31 green.
🤖 Generated with Claude Code